New bb tests#473
Conversation
Related-To: NEO-18602 Add following apis to python: 1. zesFrequencyGetProperties 2. zesPowerGetProperties 3. zesPowerGetUsage Signed-off-by: Aviral Nigam <aviral.nigam@intel.com>
Related-To: NEO-18602 Add following apis to python: 1. zesFrequencyGetProperties 2. zesPowerGetProperties 3. zesPowerGetUsage Signed-off-by: Aviral Nigam <aviral.nigam@intel.com>
Related-To: NEO-18602 Add following apis to python: 1. zesFrequencyGetProperties 2. zesPowerGetProperties 3. zesPowerGetUsage Signed-off-by: Aviral Nigam <aviral.nigam@intel.com>
Related-To: NEO-18602 Add following apis to python: 1. zesFrequencyGetProperties 2. zesPowerGetProperties 3. zesPowerGetUsage Signed-off-by: Aviral Nigam <aviral.nigam@intel.com>
Related-To: NEO-18602 Add following apis to python: 1. zesFrequencyGetProperties 2. zesPowerGetProperties 3. zesPowerGetUsage Signed-off-by: Aviral Nigam <aviral.nigam@intel.com>
Related-To: NEO-18575 Signed-off-by: Aviral Nigam <aviral.nigam@intel.com>
Related-To: NEO-18575 Signed-off-by: Aviral Nigam <aviral.nigam@intel.com>
Related-To: NEO-18602 Added following APIs to python binding: 1. zesDevicePciGetProperties 2. zesDevicePciGetStats 3. zesDeviceEccAvailable 4. zesDeviceEccConfigurable 5. zesDeviceGetEccState 6. zesDeviceSetEccState 7. zesPowerGetLimitsExt 8. zesPowerSetLimitsExt 9. zesFrequencyGetAvailableClocks 10. zesFrequencyGetRange 11. zesFrequencySetRange 12. zesFrequencyGetThrottleTime Signed-off-by: Aviral Nigam <aviral.nigam@intel.com>
Related-To: NEO-18602 Added following APIs to python binding: 1. zesDevicePciGetProperties 2. zesDevicePciGetStats 3. zesDeviceEccAvailable 4. zesDeviceEccConfigurable 5. zesDeviceGetEccState 6. zesDeviceSetEccState 7. zesPowerGetLimitsExt 8. zesPowerSetLimitsExt 9. zesFrequencyGetAvailableClocks 10. zesFrequencyGetRange 11. zesFrequencySetRange 12. zesFrequencyGetThrottleTime Signed-off-by: Aviral Nigam <aviral.nigam@intel.com>
Related-To: NEO-18602 Added following APIs to python binding: 1. zesDevicePciGetProperties 2. zesDevicePciGetStats 3. zesDeviceEccAvailable 4. zesDeviceEccConfigurable 5. zesDeviceGetEccState 6. zesDeviceSetEccState 7. zesPowerGetLimitsExt 8. zesPowerSetLimitsExt 9. zesFrequencyGetAvailableClocks 10. zesFrequencyGetRange 11. zesFrequencySetRange 12. zesFrequencyGetThrottleTime 13. zesDevicePciGetState Signed-off-by: Aviral Nigam <aviral.nigam@intel.com>
Related-To: NEO-18602 Added following APIs to python binding: 1. zesDevicePciGetProperties 2. zesDevicePciGetStats 3. zesDeviceEccAvailable 4. zesDeviceEccConfigurable 5. zesDeviceGetEccState 6. zesDeviceSetEccState 7. zesPowerGetLimitsExt 8. zesPowerSetLimitsExt 9. zesFrequencyGetAvailableClocks 10. zesFrequencyGetRange 11. zesFrequencySetRange 12. zesFrequencyGetThrottleTime 13. zesDevicePciGetState 14. zesPowerGetProperties Signed-off-by: Aviral Nigam <aviral.nigam@intel.com>
Related-To: NEO-18602 Added following APIs to python binding: 1. zesDevicePciGetProperties 2. zesDevicePciGetStats 3. zesDeviceEccAvailable 4. zesDeviceEccConfigurable 5. zesDeviceGetEccState 6. zesDeviceSetEccState 7. zesPowerGetLimitsExt 8. zesPowerSetLimitsExt 9. zesFrequencyGetAvailableClocks 10. zesFrequencyGetRange 11. zesFrequencySetRange 12. zesFrequencyGetThrottleTime 13. zesDevicePciGetState 14. zesPowerGetProperties Signed-off-by: Aviral Nigam <aviral.nigam@intel.com>
Related-To: NEO-18602 Added following APIs to python binding: 1. zesDevicePciGetProperties 2. zesDevicePciGetStats 3. zesDeviceEccAvailable 4. zesDeviceEccConfigurable 5. zesDeviceGetEccState 6. zesDeviceSetEccState 7. zesPowerGetLimitsExt 8. zesPowerSetLimitsExt 9. zesFrequencyGetAvailableClocks 10. zesFrequencyGetRange 11. zesFrequencySetRange 12. zesFrequencyGetThrottleTime 13. zesDevicePciGetState 14. zesPowerGetProperties 15. zesFrequencyGetProperties Signed-off-by: Aviral Nigam <aviral.nigam@intel.com>
Signed-off-by: Aviral Nigam <aviral.nigam@intel.com>
Signed-off-by: Aviral Nigam <aviral.nigam@intel.com>
Signed-off-by: Aviral Nigam <aviral.nigam@intel.com>
| @@ -0,0 +1,388 @@ | |||
| ## | |||
There was a problem hiding this comment.
move this to test/cts_tests/test_power_cts.py
|
|
||
| assert found_power_support, "No power handles found on any of the devices" | ||
|
|
||
| def test_GivenSamePowerHandleWhenRequestingPowerPropertiesThenExpectSamePropertiesTwiceAndLimitsAreInRange( |
There was a problem hiding this comment.
Do we need such tests which seems to be similar to L0 CTS?
@joshuaranjan thoughts?
| if not exercised_any: | ||
| pytest.skip( | ||
| "No mutable root-device power limit descriptors were available for zesPowerSetLimitsExt" | ||
| ) |
There was a problem hiding this comment.
in BMG I think we have 2 domains GPU and MEMORY which get the energy counters from PMT. So please add a test to check if L0 return insufficient permission error for these when test is not running as root.
@joshuaranjan KMD interface might be different for different platform for same APIs, what is the plan to scale these tests?
Today on BMG power APIs might return insufficient permission and the test might pass but what about next platforms?
|
please use a better commit title like |
|
As a request, your commit description needs to be a little more verbose. It is not obvious for a public repository what this is about or related to. I don't know for example what a bb test is as a maintainer of the primary L0 Loader product. |
| @@ -0,0 +1,74 @@ | |||
| ## | |||
| # Copyright (C) 2026 Intel Corporation | |||
There was a problem hiding this comment.
Move this under test/
instead of cts_tests folder name , please make it as blackbox_tests
Rename "pyzes_black_box_test.py" to pyzes_examples.py
|
|
||
| import pytest | ||
|
|
||
| CTS_TESTS_DIR = os.path.dirname(os.path.abspath(__file__)) |
There was a problem hiding this comment.
rename all the variables.
Lets avoid CTS to avoid confusion with actual conformance tests
|
|
||
|
|
||
| @pytest.fixture(scope="session") | ||
| def sysman_devices(pyzes_module): |
There was a problem hiding this comment.
What is the meaning of "conftest" ?
Is it config tests ?
No description provided.